This repository has been archived by the owner on Mar 4, 2024. It is now read-only.
EVEREST-633 Fix adding namespaces after initial install #286
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
approved these changes
Feb 9, 2024
oksana-grishchenko
approved these changes
Feb 9, 2024
recharte
force-pushed
the
EVEREST-633-fix-adding-namespaces
branch
from
e9fdb1c to
c205faa
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix adding namespaces after initial install
Problem:
EVEREST-633
With the initial implementation we weren't able to add new namespaces after initial install.
Cause:
The operator subscription was never update which lead to the DB_NAMESPACES env var not change so the everest-operator and everest BE wouldn't know about the new namespces.
Solution:
Update the subscription with a merged env var list.
CHECKLIST
Jira
Tests